In the rapidly evolving landscape of software development, where the drive toward automation often threatens to overshadow the necessity of human intellect, few voices remain as steadfast and influential as that of Michael Bolton. A software testing teacher, author, and consultant, Bolton has spent decades advocating for a paradigm shift in how we perceive the craft of testing.
As part of our "Know The Leader" series, SoftwareTestingHelp (STH) sat down with Bolton to dissect the philosophy of quality assurance, the future of the profession, and the vital importance of critical thinking in an age dominated by algorithms.
The Genesis of a Career: A Lifelong Education
Bolton’s entry into the world of software testing was not a singular moment of epiphany, but rather a convergence of various technical and analytical disciplines. His journey, he reflects, began long before he held the official title of "Software Tester."
"I could say that I became a software tester when I started editing the school newspaper, but that is too long ago to mention," Bolton jokes. His path was paved by a deep familiarity with the mechanics of software—writing code in 1988 and navigating the complexities of technical support in 1990. These formative years provided the bedrock for his professional identity, culminating in his 1994 appointment at Quarterdeck.
For Bolton, testing is not a task-oriented job but a continuous "university" that lasts an entire career. He posits that the greatest privilege of a tester is the ability to learn about technology, business domains, and complex problems—and to be compensated for that intellectual exploration.
Rapid Software Testing: Beyond the Exam
One of the most significant contributions Bolton has made to the industry is the development of the "Rapid Software Testing" (RST) methodology. Unlike traditional training programs that prioritize rote memorization and certification exams, RST focuses on the cultivation of thought.
"Lots of classes focus on memorizing terminology so that you can pass an exam," Bolton notes. "We don’t have exams."
Instead, RST emphasizes the power of vocabulary as a tool for sharper thinking. The methodology encourages practitioners to engage in deep, reflective exercises, working through puzzles and analyzing real-world testing scenarios. By collaborating with peers and debating the "why" behind their actions, testers transition from mere script-followers to active investigators. Bolton acknowledges that this approach is not entirely unique—pointing to mentors like Rob Sabourin and the BBST courses as fellow proponents of practice-based learning—but stresses that such experiential training is essential because testing is a craft that requires constant, iterative practice.
The Crisis of Competence: Challenges Facing Modern Teams
Despite the increasing reliance on software, testing teams are frequently cited as the most under-appreciated components of the development lifecycle. Bolton identifies the root of this systemic issue: a fundamental misunderstanding of the testing profession by management.
"The biggest challenge that I see is that employers misunderstand testing, and therefore hold it to a low standard," says Bolton. This creates a cycle of mediocrity. When managers view testing as a low-skill, administrative task, they hire accordingly. When testers fail to invest in their own professional development—specifically in critical thinking, systems thinking, and technical reporting—the industry’s reputation suffers further.
When asked if analytical skills or tool expertise are more critical for success, Bolton dismisses the binary choice. Comparing it to riding a bicycle, he asks, "What’s more important—keeping your balance or steering?" He argues that tools without critical thinking are useless, and thinking without the leverage of tools and process expertise is often inefficient.
The Certification Debate and the Future of Testing
In an era where certifications are often touted as the "gold standard" for career advancement, Bolton offers a sobering perspective. "Most testing certifications don’t measure your ability to test," he warns.
Instead of chasing acronyms, he advises aspiring testers to invest their time in reading the works of legends like Jerry Weinberg, participating in communities like "Weekend Testing," and taking deep-dive courses that challenge their assumptions.
Anticipating the "Check vs. Test" Divide
Bolton warns of a looming shift that may disadvantage those who refuse to evolve. He draws a firm line between "testing" and "checking."
- Checking: The rote execution of procedures where algorithms can predict outcomes.
- Testing: The intellectual, analytical process of exploring a product to find its limitations.
"Many organizations seem to think that the most important thing in testing is following someone else’s instructions," Bolton observes. "Sooner or later, people are going to realize that testing centered around confirmatory test cases is not very informative."
As automation continues to absorb the rote tasks of "checking," the value of human testers will shift toward analysis, experiment design, and social-science-based reasoning. Those who remain stagnant, clinging to manual script-following, will find themselves obsolete. Conversely, those who master the art of investigation will become the architects of quality.
The Essential Skill: Telling the Testing Story
If there is one skill that stands out as a "make or break" for modern testers, it is the ability to communicate—or as Bolton puts it, "telling the testing story."
This narrative is comprised of three distinct, intertwined strands:
- The Product Status: A transparent account of what the product does, what it fails to do, and the risks that matter to the client.
- The Testing Process: An explanation of how the product was tested, the oracles applied, the coverage achieved, and the blind spots that remain.
- The Quality of Testing: A critical assessment of why the testing performed was the best possible under the given constraints, and what is required (testability features, time, or resources) to improve future outcomes.
According to Bolton, a tester who cannot articulate these points is not fully performing their duty. They are not merely reporting bugs; they are providing the stakeholders with the information necessary to make informed business decisions.
Implications: A Call to Action
The future of software testing, as envisioned by Michael Bolton, is not one of automated complacency, but one of heightened professional rigor. He hopes to see a world where testing is recognized as a fundamental skill that pervades all of software development—a skill set that developers, designers, and business leaders alike will eventually integrate into their own workflows.
For the aspiring tester, the path forward is clear but demanding:
- Practice Critical Thinking: Constantly ask "What else could this be?"
- Improve Analytical Skills: Don’t just accept the software’s behavior; investigate its intent and its failure modes.
- Master Communication: Become a storyteller who can bridge the gap between technical reality and business risk.
"Practice what is most helpful to you in your current context," Bolton concludes. "Practice the things where you know you need to improve."
As the industry moves toward an era of hyper-automation, Bolton’s ideology serves as a crucial reminder: while machines can calculate, only humans can understand the true state of quality. For those willing to put in the work, the profession of software testing remains a boundless, intellectual, and indispensable pursuit.
